Banyan 6.0 NDIS Workstation v3.04 Banyan* NDIS workstation installation notes for Intel's EtherExpress(TM) PRO/10 ISA LAN adapters ======================================================================== Location of Driver: \NDIS\EPRO.DOS Sample Configuration Files -------------------------- CONFIG.SYS (will contain): DEVICE=C:\BAN\PROTMAN.DOS /I:C:\BAN DEVICE=C:\BAN\EPRO.DOS PROTOCOL.INI: [EPRO_NIF] Drivername = EPRO$ IOADDRESS = 0x300 General Installation -------------------- 1 The EtherExpress(TM) PRO/10 LAN adapter uses an NDIS 2.0.1 driver to connect to a Banyan server. If you have an NDIS client disk prepared, skip to step #6. 2 To generate an NDIS client disk, run PCCOPY (located on the Z drive of the Banyan server). 3 Choose PC Configuration Software and/or LAN driver, and select NDIS Ethernet and PCCONFIG. 4 Choose the appropriate DOS redirector. For example, REDIRALL for all versions of DOS. 5 Specify the directory you want the client software copied to. The default is A:\. 6 On the client you wish to set up, copy the NDIS client software to a directory on the hard drive. 7 Run Banyan's PCCONFIG program. 8 Select Network Card Settings and page down to select the NDIS Ethernet option. 9 Specify the Interrupt (as set in SoftSet2) and the PROTOCOL.INI Bindings parameter: EPRO_NIF. 10 Select Login Environment Settings, then Select Default Communications Driver. Page down to select the NDIS Ethernet option. 11 Save the settings and exit PCCONFIG. 12 Copy the files PROTOCOL.INI and EPRO.DOS that are located in the NDIS subdirectory of the EtherExpress PRO/10+ ISA LAN adapter disk to the BAN subdirectory or other directory where Banyan client files are located. Modify the PROTOCOL.INI file and remove the semi-colon in front of [EPRO_NIF] and change the IOAddress of the adapter to match the setting in SoftSet2. 13 Add the lines to your CONFIG.SYS file as shown in the Sample Configuration Files section above. 14 Reboot and run BAN to attach to the Banyan server. Hints and Tips -------------- 1 Error Message with PRO0025E This type of message will occur when the driver attempts to bind to the protocol manager. It generally indicates a syntax or other error in the PROTOCOL.INI file. Review the file carefully for errors. Also, verify parameters entered in PCCONFIG. For additional information, reference NDISBAN.DOC, which is part of the NDIS Banyan client software. 2 Make sure your NDISBAN.COM is dated April 1994 or later. Earlier versions may not work properly. 3 General parameters for the PROTOCOL.INI file are listed below. For advanced options, see the document on NDIS Driver Notes. DRIVERNAME: (required) If you have a single adapter, use the syntax in the example above. If you are installing multiple adapters, each adapter must have a unique driver name. Additional instances of the driver would be referenced by DRIVERNAME=EPROx$, where "x" would be a unique number 2 through 9. IOADDRESS: (optional for single adapter systems - except when set to certain addresses noted below) This value must match the adapter's I/O address. If the driver does not find the adapter at the specified I/O address, it will scan most of the I/O addresses that the adapter could be at and will load if it finds the adapter. The only addresses the driver doesn't scan are 2E0, 2F0 or 370. If you have used one of these address, this parameter isn't optional. If you use multiple adapters in one machine, make sure you specify the correct IOADDRESS for each board. Otherwise, the driver will fail when loading on the second card. * Third-party trademarks are the property of their respective owners.